Skip to content

Feature: HarmActEval benchmark for agent tool calls#206

Open
prane-eth wants to merge 2 commits intoconfident-ai:mainfrom
prane-eth:feature/agent-tool-harm-act-eval
Open

Feature: HarmActEval benchmark for agent tool calls#206
prane-eth wants to merge 2 commits intoconfident-ai:mainfrom
prane-eth:feature/agent-tool-harm-act-eval

Conversation

@prane-eth
Copy link

@prane-eth prane-eth commented Mar 18, 2026

Solves #202

Background

AI agents have a growing adoption across the industry, including critical applications. AI agents that have access to tools (including MCP servers) can currently call tools directly with no centralized validation layer that inspects these calls before execution, allowing harmful or disallowed tool calls to be executed without oversight.

Agent-Action-Guard introduced HarmActEval to evaluate harmful actions by agents based on harmful instructions and availability of harmful tools. The HarmActEval experiments proved GPT-5.3 has a safety score of 17.33%, which shows a very high vulnerability, proving the requirement for the evaluation. Agent-Action-Guard received 605 downloads on PyPI and 247 clones on GitHub in the first week.

Changes

I integrated HarmActEval to allow evaluation of agent safety at action-level, which was not covered by any other research or benchmarks. This allows to identify specific harmful actions taken by agents. HarmActEval is a dataset-based evaluation benchmark.

I added the dataset, benchmark, test cases, and documentation. All the test cases got passed.

@vercel
Copy link

vercel bot commented Mar 18, 2026

@prane-eth is attempting to deploy a commit to the Confident AI Team on Vercel.

A member of the Team first needs to authorize it.

@prane-eth prane-eth changed the title Added HarmActEval benchmark for agent tool calls Feature: HarmActEval benchmark for agent tool calls Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant